New Star Software Collection/NSS_Collection.iso/3-069 qemm 603/1.ima/DVMAN/APPEND-C.DEV

Text File | 1991-10-08 | 6.0 KB | 127 lines

Appendix C

Using DESQview with a Network

 DESQview can be used with most networks. The following guidelines suggest
how to deal with the four major issues of network usage:

~Item~ What the legal ramifications are of using DESQview on a network.

~Item~ How DESQview should be installed on a network.

~Item~ Why you shouldn't run DESQview on network server machines.

~Item~ How to optimize the use of DESQview on a network.

~Subhead~ Legal Considerations

 Your license agreement specifically prohibits you from assigning or
transferring DESQview to any other person. You are bound by the terms of this
license agreement when you use DESQview on a network. Each and every
individual user of DESQview on any network must have purchased (or otherwise
legally acquired) a copy of DESQview and must have a DESQview manual.

The contents of this appendix shall not be construed in any way as modifying,
qualifying, or otherwise abrogating the license agreement printed on the
inside front cover of this manual, Nor shall this appendix be construed in
any way as limiting, restricting, qualifying, or otherwise altering
Quarterdeck's legal rights and remedies under this license agreement.

~Subhead~ Installing DESQview on a Network

 DESQview can be installed on a network in several ways:

~Item~ The simplest method is for each individual user to install and run
DESQview off his own system's local hard disk, accessing the network in the
usual way.

~Item~ Another way is for each individual user to install and run DESQview
from one of his private areas on a shared disk.

~Item~ A third way is to place most of DESQview in the public area of a
shared disk and place only those files which should never be shared in a
private area.

If you use either of the first two methods, your copy of DESQview isn't
shared with other users. If you use the third method, where DESQview is
shared, you need to have a private area for the files which must not be
shared.

You must load your network before you start DESQview.  You should also log on
to the network before you start DESQview. Do not log on or off the network
from inside a DESQview window.

When DESQview needs memory, it swaps programs to your hard disk, to RAM disk,
or to expanded memory ~dash~ depending on how you've set up the SWAP drive
field of the Logical Drive setup option.  On a non-network system, the SWAP
drive is usually set to expanded memory, to a RAM disk, or to the drive and
directory from which you start up DESQview (normally C:\DV).  However, for
DESQview to function properly on a network, the SWAP drive must be set to a
unique location for each individual user. See Appendix A for the details of
how to set up the SWAP drive for different hardware configurations.

To implement the third method, where DESQview is shared, each individual
DESQview user must thus have a private area assigned to DESQview and must
start up DESQview on his local disk or on a private area of a shared disk.

~Subhead~ Installing DESQview on a Server Machine

 Many networks allow a machine to be used as both a "normal" computer and as
the network server at the same time. Do not run DESQview on a server machine.
To run a machine as a server, a special, concurrent extension to DOS is
loaded.  The server's concurrency and DESQview's concurrency will interfere
with each other and (most likely) disable or crash your server.

~Subhead~ Running DESQview with a network

 To run DESQview with a network, load your network drivers and software
first.  If possible, it is desirable to load your network (and any other)
drivers above 640K, using QEMM or QRAM, as is appropriate for your hardware.
Doing so will leave more memory below 640K for DESQview and programs.

DESQview sees a network drive as any other hard drive, and you may run
AUTOINST to automatically install the programs DESQview knows about on your
network drives as well as your local hard drives.  See page 18, Installation
Notes, for information on running AUTOINST.

~Subhead~ Optimizing DESQview on a Network

 The simple methods for installing DESQview on a network don't make the best
use of network resources, since they don't allow users to share DESQview
files. If you want to optimize DESQview usage by sharing resources, you need
to know which DESQview files can be shared, which cannot be shared, and which
can optionally be shared:

~Item~ Files that can be shared by all users are: *.EXE and *.COM.

~Item~ File that can never be shared between users are: SWAP????.DV ~dash~
the files containing the memory image of programs swapped out.

~Item~ Files that may optionally be shared are: xx-PIF.DVP, xx- SCRIP.DVS,
DESQVIEW.DVS, DESQVIEW.DVO, DESQVIEW.DVH, DESQVIEW.DIR, and DVSETUP.DV.
Normally, only DESQVIEW.DVH and DESQVIEW.DIR are shared.  The other files
usually have information that is specific to each individual user.

The fully shared and optionally shared files should be placed in a public
area.  The SWAP????.DV files should be placed on a local disk or on a private
area of a shared disk.  This is usually done by leaving the SWAP drive field
empty and then starting up DESQview with the current directory set to the
private area. (See Appendix G for a complete list of DESQview's files.)

If you want a customized version of DESQview, you should first copy all the
optionally shared files to your private area. Then, you should create a batch
file that starts up DESQview by changing to your private area, setting PATH
to include the default directory where the fully shared DESQview files are
kept, and then issuing the command to start up DESQview.  (If your network
provides a "file facility" feature,

Begin footnote

Such as APPEND on a 3COM Network and MAP SEARCH on a Novell Network

End footnote

you may put only the optionally shared files you want in your private
area.  If you don't have a file facility, all the optionally shared files
must reside in the subdirectory from which you start up DESQview.)